CD Ware Multimedia 1994 November/Cd Ware (Nro. 2) - Epimundo.iso/OS2/PC2_170.ZIP/PC2.FAQ

Text File | 1994-06-01 | 22.7 KB | 446 lines

******************************************************************************
                            Frequently asked questions

                   PC/2 - Programm Commander/2 Version 1.70 for
                         IBM OS/2 2.x Presentation Manager
                      Copyright (C) by Stangl Roman 06, 1994

                               Version 1.70 Draft
******************************************************************************

 1.) How can I configure PC/2 to popup the menu after a single-click instead
     of the default double-click with mouse button 1 on the Desktop?

     First, you may select the Configure Desktop dialog to select a default
     click which is written to the PC2.INI profile.
     Second, use the commandline option -SingleClick or /SingleClick to
     overwrite the default behaviour read from PC2.INI. If you run PC/2
     as a WPS replacement, you can't use any commandline option, because
     OS/2 seems to dislike commandline options on programs run as the WPS,
     but this doesn't prevent you from setting the default behaviour with the
     Configure Desktop dialog.

 2.) PC/2 assumes that OS/2 is installed on drive C:, but I use drive H:!

     Either start with a blank menu and add your programs, or use an editor
     f.e. EPM.EXE to replace all C: to H: in the profile.

 3.) How do I add DOS Settings correctly?

     First you should use the same spelling as in the settings of a DOS
     program. They have usually ON/OFF or numbers as possible selections.
     For ON/OFF you add =1 or =0 to the setting, f.e. HW_TIMER=1. For
     numbers add =xxxx, f.e. EMS_MEMORY_LIMIT=1024 or
     DOS_VERSION=DOSPROG.EXE,5,0,255.

 4.) How can I add batch files?

     Batch files aren't executable files, they need a command processor to
     interpret them. Therefore you have to select a command processor and
     add /C filename.bat or /C filename.cmd to the parameters entryfield.
     You may whish to look at the command reference of CMD.EXE and COMMAND.COM
     for more details. If you use the standard file dialog to find the batch
     file you want to add, PC/2 automatically add this batch file as an
     argument of an command processor.

 5.) Is HPFS supported?

     Yes, PC/2 fully supports HPFS. However, if a filename contains spaces
     you have to place it in double-quotes, f.e. at a command prompt you
     would type DIR "D:\OS!2 2.0 Desktop\*" /s to list all files of the
     Desktop directory. The same is true for PC/2, f.e. you want to start
     a batchfile that conforms HPFS-filename convention, you may create
     an entry:
        Program Title:      HPFS-Test
        Path and Filename:  C:\OS!2 2.0 Desktop\Prompts\Command Processor.exe
        Working Directory:  C:\OS!2 User Applications
        Parameters:         /C ""C:\OS!2 2.0 Desktop\Run Me.cmd""
     Note: Passing HPFS-filenames to command processors may required two
     double-quotes (f.e. CMD.EXE does). Also take a look at the help pages
     for CMD.EXE to get more details.

 6.) How do I start a full-screen WIN-OS2 session?

     Create an entry that of a full-screen DOS command prompt that starts
     WINOS2.COM (f.e. C:\OS2\MDOS\WINOS2\WINOS2.COM). Then add the required
     DOS Settings (f.e. the following settings greatly improve performance
     on a 8514/A adapter: VIDEO_8514_XGA_IOTRAP=0, VIDEO_RETRACE_EMULATION=0,
     VIDEO_SWITCH_NOTIFICATION=1, XMS=64, EMS=0, DPMI=4, IDLE_SECONDS=2,
     IDLE_SENSITIVITY=100, HW_ROM_TO_RAM=1. Thanks to Timothy Sipples for
     them!).

 7.) How do I start any windowed WIN-OS2 session type?

     Sorry, I don't know it myself. For a WIN-OS2 session you can usually
     specifying in the settings: WIN-OS2 full screen, WIN-OS2 window and
     separate session. If someone knows which OS/2 APIs are used to start
     sessions with these settings, please mail me!
     You can use MAKEOBJ.CMD to create a WPS Object with a known Object ID.
     Such an object can then be started with PC/2, so if you want to start
     a seamless WIN-OS2 session first create an object that corresponds to
     a seamless WIN-OS2 session and then use the defined object ID as the
     filename of that object to start is via PC/2.
     PC/2 allows you to start seamless WIN-OS2 session without any
     WPS Object defined, but only in separate sessions, even if the WPS
     is not running (OS/2 2.1 GA+ only!).

 8.) How do I start a VDM from an image?

     First create the image, then create an entry of a full-screen or windowed
     DOS session. Then add to the DOS settings:
        DOS_STARTUP_DRIVE=[path]DISK.IMG
     where [path]DISK.IMG is the path and filename of the image you wand to
     start. Caution! On a system (2.0 GA) it doesn't work, I don't know why.

 9.) How do I start a VDM that boots from drive A:?

     Same a item 8.) says, only adjust the DOS settings to:
        DOS_STARTUP_DRIVE=A:
     Caution! On a system (2.0 GA) the system traps, I don't know why.

10.) Why has PC/2 an option to shut down OS/2?

     Some people use PC/2 as a replacement for the WPS (that sames memory)
     and they can't click with button 2 to get the Popup Menu, from where
     shutdown can be selected.
     PC/2 requests OS/2 to clear all filebuffers. After all disk activity
     has been stopped it is safe to power off your system. PC/2 don't closes
     the programs, but after the disk activity has stopped, all processes are
     frozen (you can switch to or select programs anymore).

11.) How do I add commandline parameters a run-time?

     F.e. assume you created an Menuentry that start the editor EPM.EXE.
     After you selected EPM, just before it is started, you can request
     a dialog box from PC/2, where you can enter any commandline parameter
     by adding a [...] construct in the parameters entryfield of the Program
     Installation dialog. This work similar to the same WPS feature.

12.) How do I install PC/2 as a replacement of the WPS?

     First, install PC/2 in the normal way. Second, edit your CONFIG.SYS to
     replace the statement (you may have to use another drive name instead
     of C:):
        SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
     by
        REM * SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
        SET RUNWORKPLACE=h:\path\PC2.EXE
     where h:\path is the path where you installed PC/2 into, f.e.
     C:\PMAPPS\PC2.
     Second, add the path where PC2HOOK.DLL is installed to the LIBPATH
     environment varible in your CONFIG.SYS. PC/2 will not be loaded as a
     WPS replacement, if PC2HOOK.DLL is not in a path pointed by the
     LIBPATH environment variable (this is new to Version 1.70 because
     PC2HOOK.DLL is now statically linked).
     The next time you boot, the WPS will not be loaded (you can verify this
     by a blank screen displayed instead of the normal Desktop with objects.
     Not using the WPS saves memory and reduces boot time lightly.
     Of course you may start the WPS later, either by starting PMSHELL.EXE
     from a command prompt or from an PMSHELL Menuitem of PC/2. You can
     follow the WPS initialization by heavy disk access and buildup of your
     Desktop with objects.
     PC/2 requires to know the Desktop (in technical terms the window handle
     of the Desktop) to be able to catch mouse button 1 clicks. If you start
     the WPS the Desktop changes too. Therefor you must restart PC/2 by
     selecting PC/2 and close it from the task list. PC/2 will automatically
     restarted by OS/2 (because it is the WORKPLACE process that runs) and then
     work as before.
     PC/2 display the Window List on PM too, as the WPS does by clicking mouse
     buttons 1 an 2 together.

13.) How do I add WPS Objects to start then via PC/2?

     The important thing is, that you have to know the WPS Object ID
     (Identifier) to be able to add them to PC/2. For preinstalled Objects,
     you can find the ID in the file C:\OS2\OS2_20.RC (sorry I don't know
     any other method to get them). For user-installed Objects, you have
     to use MAKEOBJ.CMD, a small REXX-utility supplied with PC/2, to create
     an Object with a known ID. You can't use Objects created by the
     Program Template, because I don't know how to get the ID of such
     Objects, if you know how to get the ID of such Objects, p l e a s e
     mail me.
     The ID of Objects, created as outlined above, may than be added in the
     entryfield Path and Filename in the Program Installation dialog, with
     the Program Type WPS Object.
     If such an Object is a seamless WIN-OS2 session, PC/2 can also start
     such a seamless WIN-OS2 session - but remember, without an Object
     created with a known ID no seamless WIN-OS2 support with PC/2!

14.) How do I use Drag & Drop?

     Additional to the standard file dialog, you may use Drag & Drop to add
     applications in the Program Installation dialog. F.e. you may use a drive
     object, select one (1 !) application drag it into the dialog and drop it
     onto any area that accepts it (any area that isn't covered by text,
     buttons, entryfields,...).
     PC/2 will try to determine the type of the application you added
     automatically, but you may overwrite it.

15.) How can I add WPS Objects?

     If you drag WPS Objects onto the dialog, you must ensure, that the entry-
     field Path and Filename contains the correct Object ID, and the Program
     Type is WPS Object.
     For preinstalled Objects, you may need to look into OS2_20.RC to the the
     Object ID, f.e. <WP_DRIVES> or <WP_INST>.
     For user-installed Objects, use MAKEOBJ.CMD to create an Object with a
     known Object ID, f.e. <WP_WIN_PBRUSH> or <WP_WIN_WORD4WIN>.
     Then select the Object, and drag a copy over the Program Installation
     dialog and drop it on an area that accepts it.
     For preinstalled Object you have to verify that the entryfield Path and
     Filename contains the Object ID of this object.
     For user-installed Object (with MAKEOBJ.CMD) the entryfield Path and
     Filename should contain the Object ID, as long as you didn't rename the
     created Object.

16.) Does PC/2 change to the root of all drives except for the working dir?

     Yes, PC/2 changes to the root of all non-removable drives before the
     selected application is started.

17.) Which versions of OS/2 are supported?

     PC/2 was developed under OS/2 2.0 GA and OS/2 2.1 GA, but I know it
     works under the December 2.1 beta and under the March 2.1 beta too.
     PC/2 also works unter OS/2 2.11 (OS/2 2.1 GA w/ Service Pack
     installed).

18.) How do I enable the Virtual Desktop and/or sliding Focus?

     Start PC/2, click on the Desktop and select SETUP Desktop. A dialog box
     will appear where you can enable these features. Just press help for
     further information.

19.) How does the sliding Focus work?

     OS/2 generates for all pointer movements messages, that contain the
     window where the message originated. PC/2 hooks into these messages
     and determines the active window. If the active window is not the
     window that originated the message, it makes the window active, where
     the message originated. Of course, PC/2's window, the Desktop and
     the window list are treated differently.
     To preserve the Z-order of the windows, also check its option.
     Caution! The sliding Focus does not work well, if you have open
     seamless WIN-OS2 sessions.

20.) How do I use the enabled Virtual Desktop?

     You may know that f.e. a VGA-display has usually 640 columns and 480
     rows (numbered from 0...639 and 0...479). If you position your mouse
     pointer over the surrounding rows and/or columns of your display
     (here columns 0 or 639 and/or rows 0 or 479) PC/2 shifts all windows
     that exist on your system (with some exceptions like window list) in
     the opposite direction. Some windows may slide out, some may slide in
     from the other direction.
     You may click on any virtual Desktop on the overview Window to
     immediately switch to this Desktop.

21.) How does the Virtual Desktop work?

     First, for all windows OS/2 tracks their coordinates in data structures.
     PC/2 queries, and adjusts them according to the mouse movements the
     user made. F.e. if the mouse pointer is over column 0 on the screen,
     PC/2 adds to the x-position of all windows for example 50 % of the
     x-dimension of the screen. The windows appear to move rightward (out
     of the display) because the display shift leftward within the Virtual
     Desktop. Because windows are usually aligned on byte-boundaries, they
     may not appear on their original place if you shift one unit in one
     direction and one unit in the opposite direction.

22.) How do I start applications on the Virtual Desktop?

     In the Program Installation dialog, you can define the size and
     position that the application should use. You can f.e. enter
     a position of -200 in X, which would position the application left
     out of your Desktop. PC/2 forces the window to the position you entered,
     however the application may determine its size self. To allow PC/2 to
     find the window, ensure that you enter the applications Window List entry
     or titlebar text to the Session Name entryfield on the Hotkey notebook
     page of the Program Installation dialog. You don't need to enter the
     complete Window List or titlebar text, just any substring that matches
     with the text.
     However you have to ensure that the substring matches only with the
     application you want.

23.) What's the name of the Desktop?

     OS/2 2.0 introduced the name "OS/2 2.0 Desktop" for the Desktop window,
     which normally is the WPS. OS/2 2.1 will use the name "Desktop" instead,
     if you install it over a newly formatted system. OS/2 2.1 may use a
     different name, if you install it over a previous OS/2 2.0 system, so
     please read the README file provided with OS/2 2.1 carefully.
     You may use the Notebook that appears after clicking mouse button 2 on
     the WPS at page Desktop-Settings to change the Desktop's name.
     Your Desktop may have a name translated to your national language.

24.) What's the name of the Window List?

     The Window List (known as Task List in OS/2 1.x) is just named
     "Window List". It may have a name translated to your national
     language.

25.) What about seamless WIN-OS2 support, without a corresponding WPS object?

     PC/2 now allows you to start seamless WIN-OS2 sessions, but only as
     separate sessions. This means, if you start a Windows application, the
     complete WIN-OS2 environment will come up. This wastes memory, so I
     suggest to start only the Windows Program Manager from PC/2 and any
     Windows application then from the Program Manager.
     This seamless WIN-OS2 support works also without the WPS installed,
     under OS/2 2.1 GA with no problems, but OS/2 2.0 GA hangs during load.
     So under OS/2 2.0 GA only start seamless WIN-OS2 sessions if the WPS is
     running.
     Under OS/2 2.0 GA you can only successfully start WIN-OS2 sessions in
     standard mode, 386 enhanced mode in not supported by OS/2 and real mode
     starts to load, but doesn't complete successfully for unknown reasons..
     Under OS/2 2.1 GA is real mode not supported, so you may only start
     standard and 386 enhanced sessions.

26.) How many applications can I start within a seamless WIN-OS2 session?

     Usually only 1, but you may start the Windows Program Manager as the
     first and any Windows applications as a commandline parameter, which
     the Program Manager will start for you.
     If you start the Program Manager you can of course start any Windows
     application from it, but make sure, that you have enough storage defined
     in the DOS Settings (usually DPMI_MEMORY_LIMIT=16 or so).

27.) How do I define a program's priority?

     Just select the last notebook page from the Program Installation
     dialog. Warning - changing a program's priority may have severe
     impacts on your system's performance, giving nothing to the complete
     CPU time to an application.
     For example you may set a tape backup or image conversion program to
     a lower priority or a real-time data acquisition to a higher priority.
     For DOS sessions (and WIN-OS2 sessions are DOS sessions) the priority
     can't be changed, because this would lock PM for unknown reasons.

28.) How do I define a Hotkey to switch to a session?

     Just select notebook page 4 from the Program Installation dialog.
     You may define any key from the pool keys 0 to 9 and A to Z with either
     combined with the CTRL or ALT key. Once a Hotkey is defined for an
     application it is no more available for other sessions. You may define
     Hotkeys for 72 different sessions as the maximum.
     If PC/2 detects that the user pressed a Hotkey and the application the
     Hotkey is defined for is not running, PC/2 launches the application.

29.) How does the Hotkey feature work?

     PC/2 knows which Hotkeys are used if you have defined some once. PC/2
     also need to know at least a part of the session's name to switch to.
     So you have to fill the entryfield "Session Name:" with the session's
     name. For the session's name either use part of the string that
     appears in the session's titlebar, or part of the string that appears
     in the Window List for this session.
     If you press the Hotkey for a session, PC/2 searches all titlebars
     and the Window List if the text from the entryfield "Session Name:"
     is part of and switches to the session if a match was found.
     PC/2 not only switches to the session the Hotkey is defined for, but
     also onto the Virtual Desktop the session resides on.
     If neither the session's name can be found on any window's titlebar nor
     in the Window List, PC/2 assumes the application is not running and
     launches it.

30.) Why should I use the Hotkey feature?

     Well, you don't need to use it, but it may show useful to quickly switch
     to a certain session, for example a host terminal emulator and than
     switch back to a compiling environment residing on different Virtual
     Desktops.

31.) I have defined some Hotkeys now these keys are not available on other
     sessions any more!

     Once you have defined a Hotkey, this Hotkey will be "eaten" from PC/2
     when it is pressed, because if the focus is changed it doesn't make
     sense to send this key to any other window. For example if you have
     defined ALT+5 to switch to you To-do list, you want to switch to
     the To-do list when pressing ALT+5 and don't want ALT+5 sent
     to the word processor (assuming you pressed ALT+5 when the word
     processor had the focus).
     If you need a key defined as a Hotkey for another application, for
     example your spreadsheet, you have to define a different Hotkey, because
     pressing the Hotkey while having the focus on your spreadsheet (or
     any other application) does not invoke the spreadsheet's mnemonic but
     switches to another session.

32.) I switched to another session now the Hotkey feature doesn't work
     anymore!

     You have probably switched to an OS/2 session. OS/2 windowed or
     fullscreen sessions eat up all keystrokes once they have the focus
     so PC/2 doesn't get keystrokes any more. You have to switch to another
     session, before PC/2 will get keystrokes again.

33.) I defined a Hotkey but the wrong session is activated!

     You have probably defined a Hotkey for a session and have started
     more than one instance of this session. PC/2 only switched to the
     first session, that has defined a Hotkey ignoring all other sessions
     that have defined the same hotkey.
     Be sure that you don't start more than one instance of a session
     a Hotkey is defined for:

34.) How to I define a Hotkey for a certain window (f.e. Drive C object)
     even if it wasn't started from PC/2?

     Assume that you have opened the Drive C - Tree View object from the
     OS/2 System->Drives object of the WPS and you want to define ALT+C
     as its Hotkey.
     Create a new menuentry and skip to the Hotkey notebook page of the
     Program Installation dialog. Enable the Hotkey feature and select
     ALT+C as the Hotkey.
     Then select the entry of the Drive C object from the Current Window
     List MLE and doubleclick on it. The selected entry will also be
     filled into the entryfield Session Name. Now save the changes and
     voila use the newly defined Hotkey.

35.) Do I need to completely fill in the Program Installation dialog to
     define a new Hotkey?

     No, you just need to fill in the Hotkey labeled notebook page. PC/2
     uses the text entered in the entryfield Session Name to compare with
     all windows titlebars and Window List entries. If the text matches
     with any of these entries, the window the entries are defined is
     activated.
     To use the Hotkey feature just ensure that the text entered in the
     entryfield Session Name is part of any window's titlebar or Window
     List entry.

36.) I have 2 OS/2 windows with the same name. Will the Hotkey work?

     Yes, if a Hotkey is defined the first window whose titlebar or
     Window List entry matches to Session Name is activated. You have to
     ensure a unique title for a window to allow PC/2 exactly identify
     a window.

37.) How do I access the Window List on PM?

     If you are over the PM with the mouse pointer, just press and hold
     down one mouse button and then click the other while not moving the
     mouse pointer. The Window List will appear with the mouse pointer
     in center (when the complete Window List can displayed then).
     You are over the PM, if either you don't run the WPS or you moved
     the WPS to an other Virtual Desktop.
     Of course pressing CTRL+ESC works too.
     button

38.) What is the feature "Button 2 titlebar click to set window to
     bottom" useful for?

     Even if you don't use the Virtual Desktop feature, you may find that
     sometimes you like to switch to window which is behind the currently
     active one, but you don't wand to move or minimize the active one to
     get the other window to the top.
     If this option is enables just click mouse button 2 on the active
     window's titlebar to set this window to the bottom. The window
     previously behind the active window becomes now the topmost window.
     However, you can't activate window movement with mouse button 2 any-
     more, but you can do this with mouse button 1 too.

Please read also the help panels and enjoy! Roman Stangl